merge queue: checking #12694 on main (a49aada), stacked on #12695 and #12687 - #12708

The install screenshot on the Browser Extensions page framed a dashboard
sidebar that no longer exists: top-level Integrations, Config Editor,
Commands Restrictions and Event Logs entries. Those moved into the Settings
sidebar — Integrations under Developer, Config Editor and Commands
Restrictions under Configuration — so the image contradicted the step above
it, which already tells you to open Settings → Integrations and pick the
Browser category.

Only the image was stale, so this is a reshoot with no text change. The alt
text already described the Browser category and the two cards, and it still
does.

The replacement frames the content pane only — the category rail with Browser
selected, plus the Chrome Extension and Firefox Add-On cards — instead of the
whole viewport. That follows the capture conventions, which say to crop the
sidebar out unless the navigation is the point, for exactly the reason this
image rotted: a shot built around the sidebar goes stale every time a nav item
moves, even when the feature it documents has not changed. It also drops the
org name, the signed-in user's name and their avatar that the old shot carried.

Captured headless at 1440x900, retina 2x, light theme, from the mergify-sandbox
org.

Fixes Mergifyio/ci-bot#389
MRGFY-8060

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FREXr8FPsik88qcghADHcE
Change-Id: If8367fb480011d7bb31b92025a5e68d2c599f648

The Detection, Mitigation and Prevention images were captured against a
dashboard logged into an org with access to our private repositories, and they
have been served on docs.mergify.com ever since: real internal test paths, a
real pull request with its author, number and title, and a private repository
name in the selector. These three replace them with captures of
`mergify-sandbox`, an org that holds nothing private, so the same pages teach
the same thing without publishing anything.

The alternative was removing them and leaving the pages imageless, which is
what I first proposed. Replacing is better: the pages are about reading a
dashboard, and describing a donut in prose is not the same as showing one.

## What each shot shows, and that it is real

Nothing here is mocked or posed. The sandbox repository runs a real pytest
suite on a schedule through pytest-mergify, with two intentionally flaky tests,
and Test Insights has been watching it for a month.

- **Detection** — the tests-health donut (93.33% healthy, 6.67% flaky) and the
  CI Impact chart over its 141 failed executions.
- **Mitigation** — quarantine scale and impact (2 tests saved 69 times), and the
  quarantined-tests list carrying both sources, auto and manual.
- **Prevention** — caught-flaky, new-tests and CI-budget metrics, and the
  new-tests list broken down per pull request with each test's health.

Two framing decisions worth stating. All three are cropped to the content pane
rather than the whole window: a screenshot with the sidebar in frame goes stale
every time a nav item is renamed, even when the documented feature has not
moved, and that is how most of our screenshots rotted. Mitigation and
Prevention are shot over a one-month window rather than the default week,
because the week's numbers are zeros and an empty panel teaches nothing.

## What this does not do

The git history keeps the old blobs, and I would not spend a history rewrite on
them. What leaked is internal test paths, one pull request title and a private
repository name — no credentials, nothing that grants access, no customer data.
A rewrite means force-pushing main and invalidating every open pull request and
clone, and it still would not delete anything: the blobs stay reachable by SHA
until GitHub garbage-collects, forks keep their copies, and the built pages have
been crawled. What is worth doing instead is purging the CDN cache for the three
asset URLs once this lands.

MRGFY-8780
Fixes Mergifyio/ci-bot#373

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012x4fo5P6sFzCsKGZ8DDxLE
Change-Id: I98c28b4ca873d58a85b60c4df5e620145c2c10f1